Remote camera user interface

ABSTRACT

At an electronic device with a touch-sensitive display, a remote camera control user interface may be displayed. In some examples, a user may provide input through a gesture at a location corresponding to the touch-sensitive display and/or through a rotation of a rotatable input mechanism to control a camera of an external device. Camera control may include control of the external device&#39;s camera features, including image capture, zoom settings, focus settings, flash settings, and timer settings, for example, and may also include access to the external device&#39;s library of previously captured images.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 62/044,942, “Remote Camera User Interface”, filed Sep. 2, 2014, thecontent of which is hereby incorporated by reference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for providing remote camera controlon an electronic device.

BACKGROUND

Cameras, no longer limited to dedicated electronic devices, aretypically within hands reach at all times. A camera may be convenientlyincluded in any of a variety of portable electronic devices, includingsmartphones, tablet computers, and laptop computers, reducing the numberof separate devices carried by a user.

BRIEF SUMMARY

Whether for use with separate digital cameras or electronic devices withintegrated cameras, camera operators are faced with a problem: exclusionfrom their own captured images. Dedicated remote camera control devicesare available, but in contrast to the convenience of including a camerain portable electronic devices, a dedicated remote camera control istypically a large additional item for a user to carry.

In some embodiments, a method comprises: at an electronic device with atouch-sensitive display: displaying a camera affordance on thetouch-sensitive display; detecting a gesture at a location correspondingto the camera affordance; determining whether the electronic device iswirelessly connected to an external device responsive to remote cameracontrol; in accordance with a determination that the electronic deviceis wirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: displaying a remote camera user-interface on thetouch-sensitive display, wherein the remote camera user-interfacecomprises a shutter affordance; receiving data representing an imagefeed from a camera of the external device; and displaying the image feedin the remote camera user-interface; detecting a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmitting an image capture request to the externaldevice, the image capture request associated with an image capture time;and ending the display of the image feed before the image capture time.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay; one or more processors; a memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions for: displaying a camera affordance on thetouch-sensitive display; detecting a gesture at a location correspondingto the camera affordance; determining whether the electronic device iswirelessly connected to an external device responsive to remote cameracontrol; in accordance with a determination that the electronic deviceis wirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: displaying a remote camera user-interface on thetouch-sensitive display, wherein the remote camera user-interfacecomprises a shutter affordance; receiving data representing an imagefeed from a camera of the external device; and displaying the image feedin the remote camera user-interface; detecting a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmitting an image capture request to the externaldevice, the image capture request associated with an image capture time;and ending the display of the image feed before the image capture time.

In some embodiments, a non-transitory computer readable storage mediumstores one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a touch-sensitive display, cause the device to:display a camera affordance on the touch-sensitive display; detect agesture at a location corresponding to the camera affordance; determinewhether the electronic device is wirelessly connected to an externaldevice responsive to remote camera control; in accordance with adetermination that the electronic device is wirelessly connected to theexternal device and in response to the detection of a gesture at alocation corresponding to the camera affordance: display a remote camerauser-interface on the touch-sensitive display, wherein the remote camerauser-interface comprises a shutter affordance; receive data representingan image feed from a camera of the external device; and display theimage feed in the remote camera user-interface; detect a gesture at alocation corresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit an image capture request to the external device,the image capture request associated with an image capture time; and endthe display of the image feed before the image capture time.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay; means for displaying a camera affordance on the touch-sensitivedisplay; means for detecting a gesture at a location corresponding tothe camera affordance; means for determining whether the electronicdevice is wirelessly connected to an external device responsive toremote camera control; means for, in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: displaying a remote camerauser-interface on the touch-sensitive display, wherein the remote camerauser-interface comprises a shutter affordance; receiving datarepresenting an image feed from a camera of the external device; anddisplaying the image feed in the remote camera user-interface; means fordetecting a gesture at a location corresponding to the shutteraffordance; and means responsive to the detection of a gesture at alocation corresponding to the shutter affordance for: transmitting animage capture request to the external device, the image capture requestassociated with an image capture time; and ending the display of theimage feed before the image capture time.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay unit; and a processing unit coupled to the touch-sensitivedisplay unit, the processing unit configured to: enable display of acamera affordance on the touch-sensitive display unit; detect a gestureat a location corresponding to the camera affordance; determine whetherthe electronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: enable display of a remotecamera user-interface on the touch-sensitive display unit, wherein theremote camera user-interface comprises a shutter affordance; receivedata representing an image feed from a camera of the external device;and enable display of the image feed in the remote camerauser-interface; detect a gesture at a location corresponding to theshutter affordance; and in response to the detection of a gesture at alocation corresponding to the shutter affordance: transmit an imagecapture request to the external device, the image capture requestassociated with an image capture time; and end the display of the imagefeed before the image capture time.

In some embodiments, a method comprises: at an electronic device with atouch-sensitive display and a rotatable input mechanism: displaying acamera affordance on the touch-sensitive display; detecting a gesture ata location corresponding to the camera affordance; determining whetherthe electronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: displaying a remote camerauser-interface on the touch-sensitive display; receiving datarepresenting an image feed from a camera of the external device; anddisplaying the image feed in the remote camera user-interface; detectingmovement of the rotatable input mechanism; and in response to thedetection of movement of the rotatable input mechanism: resizing adisplay of the image feed in the remote camera user-interface.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay; a rotatable input mechanism; one or more processors; a memory;and one or more programs, wherein the one or more programs are stored inthe memory and configured to be executed by the one or more processors,the one or more programs including instructions for: displaying a cameraaffordance on the touch-sensitive display; detecting a gesture at alocation corresponding to the camera affordance; determining whether theelectronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: displaying a remote camerauser-interface on the touch-sensitive display; receiving datarepresenting an image feed from a camera of the external device; anddisplaying the image feed in the remote camera user-interface; detectingmovement of the rotatable input mechanism; and in response to thedetection of movement of the rotatable input mechanism: resizing adisplay of the image feed in the remote camera user-interface.

In some embodiments, a non-transitory computer readable storage mediumstores one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a touch-sensitive display and a rotatable inputmechanism, cause the device to: display a camera affordance on thetouch-sensitive display; detect a gesture at a location corresponding tothe camera affordance; determine whether the electronic device iswirelessly connected to an external device responsive to remote cameracontrol; in accordance with a determination that the electronic deviceis wirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: display a remote camera user-interface on thetouch-sensitive display; receive data representing an image feed from acamera of the external device; and display the image feed in the remotecamera user-interface; detect movement of the rotatable input mechanism;and in response to the detection of movement of the rotatable inputmechanism: resize a display of the image feed in the remote camerauser-interface.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay; a rotatable input mechanism; and means for displaying a cameraaffordance on the touch-sensitive display; means for detecting a gestureat a location corresponding to the camera affordance; means fordetermining whether the electronic device is wirelessly connected to anexternal device responsive to remote camera control; means for, inaccordance with a determination that the electronic device is wirelesslyconnected to the external device and in response to the detection of agesture at a location corresponding to the camera affordance: displayinga remote camera user-interface on the touch-sensitive display; receivingdata representing an image feed from a camera of the external device;and displaying the image feed in the remote camera user-interface; meansfor detecting movement of the rotatable input mechanism; and meansresponsive to the detection of movement of the rotatable input mechanismfor: resizing a display of the image feed in the remote camerauser-interface.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay unit; a rotatable input mechanism unit; and a processing unitcoupled to the touch-sensitive display unit and the rotatable inputmechanism unit, the processing unit configured to: enable display of acamera affordance on the touch-sensitive display unit; detect a gestureat a location corresponding to the camera affordance; determine whetherthe electronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: enable display of a remotecamera user-interface on the touch-sensitive display unit; receive datarepresenting an image feed from a camera of the external device; andenable display of the image feed in the remote camera user-interface;detect movement of the rotatable input mechanism unit; and in responseto the detection of movement of the rotatable input mechanism unit:resize a display of the image feed in the remote camera user-interface.

In some embodiments, a method comprises: at an electronic device with atouch-sensitive display and a rotatable input mechanism: displaying acamera affordance on the touch-sensitive display; detecting a gesture ata location corresponding to the camera affordance; determining whetherthe electronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: displaying a remote camerauser-interface on the touch-sensitive display; receiving datarepresenting an image feed from a camera of the external device; anddisplaying the image feed in the remote camera user-interface; detectingmovement of the rotatable input mechanism; and in response to thedetection of movement of the rotatable input mechanism: transmitting afocus setting selection to the external device.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay; a rotatable input mechanism; one or more processors; a memory;and one or more programs, wherein the one or more programs are stored inthe memory and configured to be executed by the one or more processors,the one or more programs including instructions for: displaying a cameraaffordance on the touch-sensitive display; detecting a gesture at alocation corresponding to the camera affordance; determining whether theelectronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: displaying a remote camerauser-interface on the touch-sensitive display; receiving datarepresenting an image feed from a camera of the external device; anddisplaying the image feed in the remote camera user-interface; detectingmovement of the rotatable input mechanism; and in response to thedetection of movement of the rotatable input mechanism: transmitting afocus setting selection to the external device.

In some embodiments, a non-transitory computer readable storage mediumstores one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a touch-sensitive display and a rotatable inputmechanism, cause the device to: display a camera affordance on thetouch-sensitive display; detect a gesture at a location corresponding tothe camera affordance; determine whether the electronic device iswirelessly connected to an external device responsive to remote cameracontrol; in accordance with a determination that the electronic deviceis wirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: display a remote camera user-interface on thetouch-sensitive display; receive data representing an image feed from acamera of the external device; and display the image feed in the remotecamera user-interface; detect movement of the rotatable input mechanism;and in response to the detection of movement of the rotatable inputmechanism: transmit a focus setting selection to the external device.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay; a rotatable input mechanism; and means for displaying a cameraaffordance on the touch-sensitive display; means for detecting a gestureat a location corresponding to the camera affordance; means fordetermining whether the electronic device is wirelessly connected to anexternal device responsive to remote camera control; means for, inaccordance with a determination that the electronic device is wirelesslyconnected to the external device and in response to the detection of agesture at a location corresponding to the camera affordance: displayinga remote camera user-interface on the touch-sensitive display; receivingdata representing an image feed from a camera of the external device;and displaying the image feed in the remote camera user-interface; meansfor detecting movement of the rotatable input mechanism; and meansresponsive to the detection of movement of the rotatable input mechanismfor: transmitting a focus setting selection to the external device.

In some embodiments, an electronic device comprises: a touch-sensitivedisplay unit; a rotatable input mechanism unit; and a processing unitcoupled to the touch-sensitive display unit and the rotatable inputmechanism unit, the processing unit configured to: enable display of acamera affordance on the touch-sensitive display unit; detect a gestureat a location corresponding to the camera affordance; determine whetherthe electronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: enable display of a remotecamera user-interface on the touch-sensitive display unit; receive datarepresenting an image feed from a camera of the external device; andenable display of the image feed in the remote camera user-interface;detect movement of the rotatable input mechanism unit; and in responseto the detection of movement of the rotatable input mechanism unit:transmit a focus setting selection to the external device.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6 illustrates exemplary user interfaces for providing remote cameracontrol.

FIG. 7 illustrates exemplary user interfaces for providing remote cameracontrol.

FIG. 8 illustrates exemplary user interfaces for providing remote cameracontrol.

FIG. 9 illustrates exemplary user interfaces for providing remote cameracontrol.

FIG. 10 illustrates exemplary user interfaces for providing remotecamera control.

FIG. 11 illustrates exemplary user interfaces for providing remotecamera control.

FIG. 12 illustrates exemplary user interfaces for providing remotecamera control.

FIG. 13 illustrates exemplary user interfaces for providing remotecamera control.

FIG. 14 illustrates exemplary user interfaces for providing remotecamera control.

FIG. 15 is a flow diagram illustrating a process for providing remotecamera control user interfaces.

FIG. 16 is a flow diagram illustrating a process for providing remotecamera control user interfaces.

FIG. 17 is a flow diagram illustrating a process for providing remotecamera control user interfaces.

FIG. 18 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 19 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 20 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 21 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

As discussed above, a user may wish to have remote camera control,without carrying a relatively large additional item. Camera control mayinclude control of an external device's camera features, including imagecapture, zoom settings, focus settings, flash settings, and timersettings, for example, and may also include access to the externaldevice's library of previously captured images. It is desirable toprovide remote camera control in a reduced-sized electronic device toreduce the user's burden.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, 5A-5B, and 18-21 provide a descriptionof exemplary devices for performing the techniques for providing remotecamera control user interfaces. FIGS. 6-14 illustrate exemplary userinterfaces for providing remote camera control on these exemplarydevices. FIGS. 15-17 are flow diagrams illustrating methods of providingremote camera control user interfaces. The user interfaces in FIGS. 6-14are also used to illustrate the processes described below, including theprocesses in FIGS. 15-17.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Patents: U.S. Pat. No. 6,323,846 (Westerman et al.), U.S.Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 1500-1700 (FIGS. 15-17).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on a multifunctiondevice with a display and a touch-sensitive surface, such as devices100, 300, 500, 1800, 1900, 2000, and/or 2100 (FIGS. 1A, 3A, 5A, and/or18-21), to provide remote camera control to a user on a reduced-sizedevice.

The user interfaces for providing remote camera control (also referredto as “remote camera user interfaces”) described below are illustratedby exemplary sequences of screens that one or more of devices 100, 300,and/or 500 can display in response to detecting various user inputs. Inthese sequences, the arrows indicate the order in which the screens aredisplayed, and the text shown above the arrows indicates exemplaryinputs detected by the device. The device may respond similarly todifferent inputs; not all possible inputs that can result in thedepicted sequence of screens are shown.

FIG. 6 shows exemplary user interface screen 602 that device 600 candisplay on touchscreen 604. Device 600 is a multifunction device 500 insome embodiments. Screen 602 can be, for example, a home screen thatappears when the display of device 600 is powered on, or that appears inresponse to user input on device 600. Screen 602 displays affordancesthat may be used to launch software applications installed on device600.

Affordance 606 corresponds to a remote camera control application inthat the remote camera control application may launch in response to auser's selection of affordance 606. A remote camera control applicationmay enable a user of device 600 to wirelessly control camera functionsof an external device (e.g., a camera of device 100 in FIG. 4A).

Camera control optionally includes control of the external device'scamera features, including image capture, zoom settings, focus settings,flash settings, and timer settings, for example. Camera control may alsoinclude access to the external device's library of previously capturedimages. In some embodiments, the camera is installed in a housing of theexternal device. In other embodiments, the camera is not installed in ahousing of the external device, but is controlled by the externaldevice.

A user may select (e.g., make touch contact) with affordance 606 tolaunch the remote camera control application. In response to detecting auser's selection of affordance 606 and determining that device 600 iswirelessly connected to an external device responsive to remote cameracontrol, device 600 launches the remote camera control application anddisplays a user interface screen 608 conveying affordances for providingcontrol of a camera of the external device. If device 600 determinesthat device 600 is not connected to an external device responsive toremote camera control, device 600 may take other actions, includingproviding a visual notification that remote camera control is notavailable (as described further below), reviewing captured images thatare stored on the electronic device, or storing flash, zoom, or timersettings for a future wireless connection with the external device.Determining whether device 600 is wirelessly connected to an externaldevice responsive to remote camera control optionally occurs before, atthe same time, or after detecting a user's selection of affordance 606.

In some embodiments, the external device is preselected by a user ofdevice 600. In other embodiments, device 600 displays affordances (notshown) for a list of available external devices responsive to cameracontrol by device 600, in response to selection of affordance 606.

Device 600 receives data from the external device representing an imagefeed from the camera of the external device, in response to detectingselection of affordance 606 and a determination that device 600 isconnected to an external device that is responsive to remote cameracontrol. In some embodiments, an image feed represents a scene in realtime or with some processing delay. Device 600 displays the image feed610 on the user interface 608.

In some embodiments, image feed 610 includes a representation of theuser of device 600. Advantageously, this arrangement may allow the userof device 600 to retain control of the camera operations and also to beincluded in the captured image. The effect of this feature may be toadvantageously alleviate some known problems with prior art remotedevices—a user was typically unable to evaluate a scene with the user init, especially a scene that cannot be captured by holding and reversinga camera (e.g. a “selfie”).

Image feed 610 includes a representation 614 of device 600. This mayoccur, for example, when device 600 is wearable by the user (such asattached to the wrist of the user). In this example, when the user isincluded in the image feed, then a representation 614 of device 600 mayalso be included in the image feed. The representation 614 of device 600also includes a representation 616 of the image feed that is currentlydisplayed in the remote camera control user interface.

In some embodiments, remote camera user-interface 608 includes a shutteraffordance 612. In response to detection of a gesture at a locationcorresponding to the shutter affordance, device 600 transmits an imagecapture request to the external device. The image capture request isassociated with an image capture time.

The image capture request is optionally a request for an instantaneouscapture, e.g., the image is captured when the external device receivesthe request. In such an embodiment, the image capture time is the sameinstant the image capture request is transmitted. In some embodiments,the image capture time is estimated based on a timer setting, or isbased on an estimated processing lag. In some embodiments, the imagecapture request includes the image capture time, e.g., by including arequested image capture time.

In some embodiments, device 600 ends the display 618 of the image feed610 before the image capture time. In this way, embodiments describedherein may advantageously allow for capture of the scene withoutdepicting the image feed. The effect of this feature may be to improvethe resulting captured image—a later viewer of the captured image is notreminded of the process of taking the picture using device 600, therebyproviding a more causal and natural captured image.

In some embodiments, device 600 ends the display of the image feed byreplacing the display of the remote camera user-interface with a displayof a screen selected from the group consisting of a home screen, a blankscreen, and a watch face. In some other embodiments, device 600 ends thedisplay of the image feed by turning off the display.

User interface 608 may be too large to be displayed completely on-screenat one time. When a first portion of user interface 608 is displayed, auser may rotate rotatable input mechanism 620 in a particular direction(e.g., rotation 622) to scroll the displayed portion of user interface608 to display the second portion.

In some embodiments, scrolling the first user interface includestranslating the first user interface screen on-screen. In someembodiments, the extent of rotation is proportional to the amount ofscrolling of the display (e.g., on-screen translation). In thisscenario, a smaller rotation scrolls the displayed portion of the userinterface less than a larger rotation. Relating the extent of rotationof the rotatable input mechanism 620 allows the user to preciselycontrol which content(s) of the user interface are to be viewed.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 7. FIG. 7 showsexemplary user interface screen 702 that device 700 can display on atouchscreen. In some embodiments, device 700 is device 500 (FIG. 5).User interface 702 is optionally a remote camera control user interface,and includes an image feed 704 received from a camera of an externaldevice (not shown). User interface 702 includes a shutter affordance706. In some embodiments, remote camera control user interface 702 isdisplayed in response to detecting a user's selection of a cameraaffordance from a user interface of device 700.

Device 700 includes a rotatable input mechanism 708. Rotatable inputmechanism 708 is optionally configured to enable a user to alter zoom ofthe image feed. To alter zoom, a user may rotate rotatable inputmechanism 708 in direction 710. In response to detecting movement of therotatable input mechanism 708, device 700 resizes the display of theimage feed 712 in the remote camera user-interface.

In the exemplary embodiment of FIG. 7, a counterclockwise rotation ofrotatable input mechanism 708 resulted in a “zoom-in” of the image, thatis, the size of image feed is increased in the display. In someembodiments, a clockwise rotation of rotatable input mechanism 708results in “zoom-out” of the image, that is, the size of the image feedis decreased in the display. In some embodiments, the amount of resizingis linearly related to the degree of rotation. In other embodiments, theamount of resizing is non-linearly related to the degree of rotation.

In some embodiments, a zoom setting selection is transmitted to theexternal device, in response to detecting movement of the rotatableinput mechanism. In some embodiments, the zoom setting selection istransmitted immediately in response to detecting movement of therotatable input mechanism. In this way, the external device can alterthe zoom setting on the associated camera and the image feed from theexternal device to device 700 can be updated. This may have theadvantageous effect of providing the user with a real-time view of thecamera's zoomed in image. In other embodiments, the zoom settingselection is transmitted to the external device with an image capturerequest. In this way, device 700 can send one zoom request to theexternal device while allowing the user to zoom the image to variouslevels when preparing to capture an image. This may have theadvantageous effect of reducing the wireless communication with theexternal devices and limiting expenditure of processing resources of theexternal device.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 8. FIG. 8 showsexemplary user interface screen 802 that device 800 can display on atouchscreen. In some embodiments, device 800 is device 500 (FIG. 5).User interface 802 is a remote camera control user interface, andincludes an image feed 804 received from a camera of an external device(e.g., a camera of device 100 in FIG. 4A). User interface 802 includes ashutter affordance 806. In some embodiments, remote camera control userinterface 802 is displayed in response to detecting a user's selectionof a camera affordance from a user interface of device 800.

Device 800 includes a rotatable input mechanism 808. Rotatable inputmechanism 808 is configured to enable a user to change the focus of thecamera of the external device. To change focus, a user may rotaterotatable input mechanism 808 in direction 810. In response to detectingmovement of the rotatable input mechanism 808, device 800 transmits afocus setting selection to the external device.

As used herein, a “focus setting” refers to a camera setting thatcontrols how the convergence of light is captured by the camera todefine a part of the image that is “in focus” and other parts as being“out of focus” based on distance from the camera.

Device 800 also provides a visual indication of the focus setting 814.In the example provided in FIG. 8, a broken square depicts the selectionof the focus setting, but other visual indications could be used withoutdeviating from the scope of the claimed subject matter.

In some embodiments, the focus setting is coupled with a face detectionsystem. The face detection system may change the focus successivelybetween faces detected in the image feed. In response to detecting amovement of rotatable input mechanism 808 in direction 812, device 800changes the focus setting to another face detected in the image feed.Device 800 optionally provides a visual indication of the new focussetting 816.

In some embodiments, the focus setting selection incrementally moveswithin the user interface. For example, a visual indication (such as thebroken square discussed above) moves a distance across the image feed(for example, moving between points on a grid). Once the visualindication has stopped moving, a focus setting corresponding to thelocation of the visual indication is transmitted to the external device.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 9. FIG. 9 showsexemplary user interface screen 902 that device 900 can display on atouchscreen. In some embodiments, device 900 is device 500 (FIG. 5).User interface 902 is a remote camera control user interface, andincludes an image feed 904 received from a camera of an external device(not shown). User interface screen 902 includes a shutter affordance906. In some embodiments, remote camera control user interface 902 isdisplayed in response to detecting a user's selection of a cameraaffordance from a user interface of device 900.

Device 900 includes a rotatable input mechanism 908. In someembodiments, user interface 902 includes toggle affordance 910 thatnotifies the user of an action associated with movement of rotatableinput mechanism 908. For example, toggle affordance 910 includes an “F,”indicating that movement of the rotatable input mechanism 908 willprovide focus functionality, such as that described above with respectto FIG. 8 and device 800. In some embodiments (not shown), the toggleaffordance is presented a toggle switch that is actuated between a firstposition associated with a first function and a second positionassociated with a second function.

In response to detecting a contact on toggle affordance 910, an actionassociated with detecting movement of the rotatable input mechanism 908is changed. In the example of FIG. 9, the action is changed from one oftransmitting a focus setting selection to the external device toresizing the display of the image feed in the remote camerauser-interface. To reflect this change in an action associated withdetecting movement of the rotatable input mechanism 908, toggleaffordance 912 includes a “Z” to reflect the zoom setting selection nowassociated with rotatable input mechanism 908. Movement of the rotatableinput mechanism 908 will now provide zoom functionality, such as thatdescribed above with respect to FIG. 7 and device 700.

Descriptions of rotatable input mechanisms (such as rotatable inputmechanisms 506, 620, 708, 808, and 908) described herein have primarilyrelated to control camera features (such as preview, zoom, focus, andcapturing images). It should be noted that the rotatable inputmechanisms of electronic devices 500, 600, 700, 800, and 900 can providea variety of other functions included on the electronic device(s). Inother embodiments, rotatable input mechanisms 506, 620, 708, 808, and908 provide, for example, resizing or scrolling a home page orspringboard, scrolling between geographic locations (e.g., cities) in aweather application, scrolling through playlists in a music playerapplication, adjusting volume in an audio application, scrolling throughnames in a contacts application, and changing the view angle/perspectivein a clock face application.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 10. FIG. 10shows exemplary user interface screen 1002 that device 1000 can displayon touchscreen 1004. In some embodiments, device 1000 is device 500(FIG. 5). User interface 1002 is a remote camera control user interface,and includes an image feed 1004 received from a camera of an externaldevice (e.g., a camera of device 100 in FIG. 4A). User interface 1002includes a shutter affordance 1006. In some embodiments, remote cameracontrol user interface 1002 is displayed in response to detecting auser's selection of a camera affordance from a user interface of device1000.

In some embodiments, user interface 1002 includes flash affordance 1008.In response to detecting contact on flash affordance 1008, device 1000transmits a camera flash selection to the external device. The cameraflash selection may include one of an auto flash, flash on, and flashoff, which may correspond to a camera flash setting of the externaldevice. As the user contacts the flash affordance, the flash affordancechanges from auto flash (1008), to flash on (1010), and flash off(1012). In some embodiments, the flash setting is transmitted to theexternal device at the time of selection. In some embodiments, the flashsetting is transmitted to the external device with an image capturerequest.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 11. FIG. 11shows exemplary user interface screen 1102 that device 1100 can displayon touchscreen 1104. In some embodiments, device 1100 is device 500(FIG. 5). User interface 1102 is a remote camera control user interface,and include an image feed 1104 received from a camera of an externaldevice (e.g., a camera of device 100 in FIG. 4A). In some embodiments,remote camera control user interface 1102 is displayed in response todetecting a user's selection of a camera affordance from a userinterface of device 1100.

In some embodiments, user interface 1102 includes timer affordance 1108.In response to detecting contact on timer affordance 1108, device 1000transmits a timer setting selection to the external device. The timersetting selection includes one of a no timer, a two-second timer, and aten-second timer, which may correspond to a timer setting of theexternal device. As the user contacts the timer affordance, the timeraffordance changes from no timer (1108), a two-second timer (1110), or aten-second timer (1112).

In some embodiments, the timer setting is transmitted to the externaldevice upon detection of a contact on shutter affordance 1106. An imagecapture request associated with shutter affordance is delayed to accountfor the timer request; that is, device 1100 may transmit a request tothe external device to immediately capture an image, only after device1100 determines that the appropriate time has expired. In someembodiments, a requested image capture time is transmitted with theimage capture request, wherein the requested image capture time accountsfor a timer setting associated with the timer affordance.

In some embodiments, device 1100 displays a count-down to an imagecapture time in response to detection of a contact on shutter affordance1106 and a non-zero timer setting. For example, for a two-second timersetting, device 1100 displays a count down from two seconds to onesecond to zero. In some embodiments, the count-down is displayed as adecreasingly-filled ring.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 12. FIG. 12shows exemplary user interface screen 1202 that device 1200 can displayon touchscreen 1204. User interface screen 1202 includes a shutteraffordance 1206. In some embodiments, device 1200 is device 500 (FIG.5). User interface 1202 is a remote camera control user interface, andincludes an image feed 1204 received from a camera of an external device(e.g., a camera of device 100 in FIG. 4A). In some embodiments, remotecamera control user interface 1202 is displayed in response to detectinga user's selection of a camera affordance from a user interface ofdevice 1200.

In response to a contact on image feed 1202 on touch screen 1204, device1200 transmits a focus setting selection to the external device. Device1200 provides a visual indication of the focus setting 1208. In theexample provided in FIG. 12, a broken square depicts the selection ofthe focus setting, but other visual indications could be used withoutdeviating from the scope of the claimed subject matter.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 13. FIG. 13shows exemplary user interface screen 1302 that device 1300 can displayon touchscreen 1304. In some embodiments, device 1200 is device 500(FIG. 5). Screen 1302 can be, for example, a home screen that appearswhen the display of device 600 is powered on, or that appears inresponse to user input on device 1300. Screen 1302 displays affordancesthat optionally launch software applications installed on device 1300.

Affordance 1306 may correspond to a remote camera control application inthat the remote camera control application may launch in response to auser's selection of affordance 1306. A remote camera control applicationmay enable a user of device 1300 to wirelessly control camera functionsof an external device (e.g., a camera of device 100 in FIG. 4A).

A user may select affordance 1306 to launch the remote camera controlapplication. In response to detecting a user's selection of affordance1306 and determining that device 1300 is not wirelessly connected to anexternal device responsive to remote camera control, device 1300displays screen 1308 which notifies the user that the external device isnot available for remote camera control. In some embodiments, device1300 displays captured images that are stored on device 1300, or storesflash, zoom, or timer settings for a future wireless connection with theexternal device. Display screen 1308 is exemplary and, as will bereadily understood by a person having ordinary skill in the art, otherimages could be used to notify a user that the external device is notavailable for remote camera control.

Attention is now directed to a remote camera control user interface thatis displayed in some embodiments, with reference to FIG. 14. FIG. 14shows exemplary user interface screen 1402 that device 1400 can displayon touchscreen 1404. User interface screen 1402 includes a shutteraffordance 1406. In some embodiments, device 1400 is device 500 (FIG.5). User interface 1402 is a remote camera control user interface, andinclude an image feed 1404 received from a camera of an external device(e.g., a camera of device 100 in FIG. 4A) and an image previewaffordance 1408. In some embodiments, remote camera control userinterface 1402 is displayed in response to detecting a user's selectionof a camera affordance from a user interface of device 1400.

In some embodiments, image preview affordance 1408 is a thumbnail of animage of a photo album of the external device. A user may select imagepreview affordance 1408. In response to detecting a selection of theimage preview affordance, device 1400 displays one or more images 1410of the photo album of the external device. Device 1400 optionallydisplays “Roll” affordance 1412. A user may select roll affordance 1412to access more images of the photo album of the external device. Inresponse to detecting a selection of roll affordance 1412, device 1400display a plurality of images of the photo album of the external device.

Device 1400 optionally displays “Done” affordance 1414. A user mayselect done affordance 1414 to close the display of the one or moreimages of the photo album of the external device.

Although user interfaces 602, 608, 702, 802, 902, 1002, 1102, 1202,1302, and 1402 have been described with respect to controlling camerafeatures of an external device, it should be appreciated that these userinterfaces can also be used for controlling a camera included withelectronic devices 600, 700, 800, 900, 1000, 1100, 1200, 1300, or 1400.For example, user interfaces 602, 608, 702, 802, 902, 1002, 1102, 1202,1302, and 1402 can be used to launch a camera application, capture animage, change zoom, change focus, change a zoom/focus setting associatedwith a rotatable input mechanism, change a flash, change a timer, orpreview captured images of a camera included with electronic devices600, 700, 800, 900, 1000, 1100, 1200, 1300, or 1400.

FIG. 15 is a flow diagram illustrating process 1500 for providing aremote camera control user interface. In some embodiments, process 1500is performed at an electronic device with a display (e.g., 112, 340,504, 1802) and a rotatable input mechanism (e.g., 506, 620, 708, 808,908). In some embodiments, the electronic device also includes atouch-sensitive surface (e.g., 112, 355, 504, 1804). Some operations inprocess 1500 may be combined, the order of some operations may bechanged, and some operations may be omitted.

Process 1500 provides an intuitive way to remotely control a camera ofan external device. A user can retain control of the camera operations,while being included in the captured image. The process reduces thecognitive burden on a user when using a device to control a camera of anexternal device, thereby creating a more efficient human-machineinterface. The process allows a user to evaluate a scene with the userin it, especially a scene that cannot be captured by holding andreversing a camera (e.g. a “selfie”). Process 1500 may also improve thequality of captured images-a later viewer of the captured image(s) isnot reminded of the process of taking the picture, thereby providing amore causal and natural captured image. For battery-operated computingdevices, enabling a user control a camera of an external device morequickly and more efficiently conserves power and increases the timebetween battery charges.

At block 1502, a camera affordance (e.g., 606, 1306) is displayed on thetouch-sensitive display. At block 1504, a contact on the displayedcamera affordance (e.g., 606, 1306) is detected. At block 1506, adetermination is made as to whether the electronic device is wirelesslyconnected to an external device responsive to remote camera control. Atblock 1508, responsive at least in part to detecting the contact anddetermining the electronic device is wirelessly connected to theexternal device, a remote camera user-interface (e.g., 608, 702, 902,902, 1002, 1102, 1202, and 1402) is displayed, wherein the remote camerauser-interface (e.g., 608, 702, 902, 902, 1002, 1102, 1202, and 1402)comprises a shutter affordance (e.g., 612, 706, 806, 906, 1006, 1106,and 1206). At block 1510, data representing an image feed from a cameraof the external device is received. At block 1512, the image feed isdisplayed (e.g., 610, 704, 804, 904) in the remote camera user-interface(e.g., 608, 702, 902, 902, 1002, 1102, 1202, and 1402). At block 1514, acontact is detected on the shutter affordance (e.g., 612, 706, 806, 906,1006, 1106, and 1206). At block 1516, responsive at least in part todetecting the contact on the shutter affordance (e.g., 612, 706, 806,906, 1006, 1106, and 1206), an image capture request is transmitted tothe external device, wherein the image capture request is associatedwith an image capture time. At block 1518, the display of the image feedis ended before the image capture time. Optionally, at block 1518, thedisplay of the remote camera user-interface is replaced with a displayof a screen selected from the group consisting of a home screen, a blankscreen, and a watch face. Optionally, at block 1518, the display isturned off.

FIG. 16 is a flow diagram illustrating process 1600 for providing aremote camera control user interface. In some embodiments, process 1600is performed at an electronic device with a display (e.g., 112, 340,504, 1802) and a rotatable input mechanism (e.g., 506, 620, 708, 808,908). In some embodiments, the electronic device also includes atouch-sensitive surface (e.g., 112, 355, 504, 1804). Some operations inprocess 1600 may be combined, the order of some operations may bechanged, and some operations may be omitted.

Process 1600 provides an intuitive way to remotely control a camera ofan external device. A user can retain control of the camera operations,while being included in the captured image. The process reduces thecognitive burden on a user when using a device to control a camera of anexternal device, thereby creating a more efficient human-machineinterface. The process allows a user to evaluate a scene with the userin it, especially a scene that cannot be captured by holding andreversing a camera (e.g. a “selfie”). In some optional embodiments,process 1600 reduces wireless communication with an external device andlimit expenditure of processing resources of the external device. Insome optional embodiments, process 1600 provides the user with areal-time view of the camera's zoomed in image. For battery-operatedcomputing devices, enabling a user control a camera of an externaldevice more quickly and more efficiently conserves power and increasesthe time between battery charges.

At block 1602, a camera affordance (e.g., 606, 1306) is displayed on thetouch-sensitive display. At block 1604, a contact on the displayedcamera affordance (e.g., 606, 1306) is detected. At block 1606, adetermination is made as to whether the electronic device is wirelesslyconnected to an external device responsive to remote camera control. Atblock 1608, responsive at least in part to detecting the contact anddetermining the electronic device is wirelessly connected to theexternal device, a remote camera user-interface (e.g., 608, 702, 902,902, 1002, 1102, 1202, 1402) is displayed. At block 1610, datarepresenting an image feed from a camera of the external device isreceived. At block 1612, the image feed is displayed (e.g., 610, 704,804, 904) in the remote camera user-interface (e.g., 608, 702, 902, 902,1002, 1102, 1202, 1402). At block 1614, movement of the rotatable inputmechanism (e.g., 506, 620, 708, 808, 908) is detected. At block 1616,responsive at least in part to detection of movement of the rotatableinput mechanism (e.g., 506, 620, 708, 808, 908), a display of the imagefeed is resized (e.g., 712). Optionally, at block 1616, a zoom settingselection is transmitted to the external device. Optionally, at block1616, a contact on a shutter affordance (e.g., 612, 706, 806, 906, 1006,1106, and 1206) of the user interface is detected and, at leastpartially in response to detecting a contact on the shutter affordance(e.g., 612, 706, 806, 906, 1006, 1106, and 1206), an image capturerequest and a zoom setting selection are transmitted to the externaldevice.

FIG. 17 is a flow diagram illustrating process 1700 for providing aremote camera control user interface. In some embodiments, process 1700is performed at an electronic device with a display (e.g., 112, 340,504, 1802) and a rotatable input mechanism (e.g., 506, 620, 708, 808,908). In some embodiments, the electronic device also includes atouch-sensitive surface (e.g., 112, 355, 504, 1804). Some operations inprocess 1700 may be combined, the order of some operations may bechanged, and some operations may be omitted.

Process 1700 provides an intuitive way to remotely control a camera ofan external device. A user can retain control of the camera operations,while being included in the captured image. The process reduces thecognitive burden on a user when using a device to control a camera of anexternal device, thereby creating a more efficient human-machineinterface. The process allows a user to evaluate a scene with the userin it, especially a scene that cannot be captured by holding andreversing a camera (e.g. a “selfie”). For battery-operated computingdevices, enabling a user control a camera of an external device morequickly and more efficiently conserves power and increases the timebetween battery charges.

At block 1702, a camera affordance (e.g., 606, 1306) is displayed on thetouch-sensitive display. At block 1704, a contact on the displayedcamera affordance (e.g., 606, 1306) is detected. At block 1706, adetermination is made as to whether the electronic device is wirelesslyconnected to an external device responsive to remote camera control. Atblock 1708, responsive at least in part to detecting the contact anddetermining the electronic device is wirelessly connected to theexternal device, a remote camera user-interface (e.g., 608, 702, 902,902, 1002, 1102, 1202, and 1402) is displayed. At block 1710, datarepresenting an image feed from a camera of the external device isreceived. At block 1712, the image feed is displayed (e.g., 610, 704,804, 904) in the remote camera user-interface (e.g., 608, 702, 902, 902,1002, 1102, 1202, and 1402). At block 1714, movement of the rotatableinput mechanism (e.g., 506, 620, 708, 808, 908) is detected. At block1716, responsive at least in part to detection of movement of therotatable input mechanism (e.g., 506, 620, 708, 808, 908), a focussetting selection is transmitted to the external device. Optionally, atblock 1716, a contact on a shutter affordance (e.g., 612, 706, 806, 906,1006, 1106, and 1206) of the user interface is detected and, at leastpartially in response to detecting a contact on the shutter affordance(e.g., 612, 706, 806, 906, 1006, 1106, and 1206), an image capturerequest and the focus setting selection are transmitted to the externaldevice.

It should be understood that the particular order in which theoperations in FIGS. 15-17 have been described is exemplary and notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.For brevity, these details are not repeated here. Additionally, itshould be noted that aspects of processes 1500-1700 (FIGS. 15-17) may beincorporated with one another. For brevity, the permutations of userinput techniques are not repeated.

The operations described above with reference to FIGS. 15-17 are,optionally, implemented by components depicted in FIGS. 1A-1B, 5A-5B,and 18. For example, operations 1504, 1506, 1508, 1514, 1516, 1518,1604, 1606, 1608, 1614, 1616, 1704, 1706, 1708, 1714, and 1716 are,optionally implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B, 5A-5B and 18.

It should also be understood that the embodiments described above withrespect to FIGS. 6-17 may be complemented by additional features. Forexample, the embodiments may be complimented with methods and systemsfor displaying elements in greater detail and accessing information on adevice, including the methods and systems described in U.S. Pat. No.8,773,470, issued on Jul. 8, 2014 (filed May 7, 2010 as U.S. patentapplication Ser. No. 12/776,331), titled “Systems and methods fordisplaying visual information on a device,” which is incorporated hereinby reference in its entirety.

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A, 1B, 3, 5A, 5B, and 18) are all included within thescope of protection of the invention.

FIG. 18 shows exemplary functional blocks of an electronic device 1800that, in some embodiments, performs the features described above. Asshown in FIG. 18, an electronic device 1800 includes a display unit 1802configured to display graphical objects; a touch-sensitive surface unit1804 configured to receive user gestures; one or more RF units 1806configured to detect and communicate with external electronic devices;and a processing unit 1808 coupled to display unit 1802, touch-sensitivesurface unit 1804, and RF unit(s) 1806. In some embodiments, processingunit 1808 is configured to support an operating system 1810 forlaunching and running one or more applications 1812.

In some embodiments, the processing unit 1808 includes a displayenabling unit 1814, a detecting unit 1816, a determining unit 1818, andan obtaining unit 1820. In some embodiments, the display enabling unit1814 is configured to cause a display of a user interface (or portionsof a user interface) in conjunction with the display unit 1802. Forexample, the display enabling unit 1814 may be used for: displaying anaffordance, displaying a user interface screen or a portion thereof,displaying a wallpaper, displaying indications (such as indications oftemperature or location), displaying remote camera control userinterfaces, displaying a grid or a plurality of regions, and displayingan image. In some embodiments, the detecting unit 1816 is configured toreceive input, e.g., through the use of touch-sensitive surface unit1804. For example, the detecting unit 1816 may be used for: detecting acontact, detecting movement of the rotatable input mechanism, anddetecting a swipe. In some embodiments, the determining unit 1818 isconfigured to make determinations. For example, determining unit 1818may be used for: determining whether a user input is movement of therotatable input mechanism or a swipe on the touch-sensitive display, anddetermining that an activity is to begin with a threshold amount oftime. In some embodiments, the obtaining unit 1820 is configured toobtain information. For example, the obtaining unit 1820 may be used forobtaining camera data from an external device, including an image feedand captured images of a photo album of the external device. The unitsof FIG. 18 may be used to implement the various techniques and methodsdescribed above with respect to FIGS. 6-17.

The functional blocks of the device 1800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 18 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

In accordance with some embodiments, FIG. 19 shows an exemplaryfunctional block diagram of an electronic device 1900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1900 are configured to perform the techniques described above.The functional blocks of the device 1900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 19 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 19, an electronic device 1900 includes atouch-sensitive display unit 1920 configured to display a graphic userinterface, and a processing unit 1926 coupled to touch-sensitive displayunit 1920. In some embodiments, processing unit 1926 includes a displayenabling unit 1930, an input detecting unit 1932, a wireless connectiondetermining unit 1934, a data receiving unit 1936, and a transmittingunit 1938. Optionally, electronic device 1900 also includes a rotatablemechanism unit 1922, which is coupled to processing unit 1926.Optionally, processing unit 1926 also includes an action changing unit1940.

Processing unit 1926 is configured to: enable (e.g., with displayenabling unit 1930) display of a camera affordance on touch-sensitivedisplay unit 1920; detect (e.g., with input detecting unit 1932) agesture at a location corresponding to the camera affordance; determine(e.g., with wireless connection determining unit 1934) whetherelectronic device 1900 is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat electronic device 1900 is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: enable (e.g., with displayenabling unit 1930) display of a remote camera user-interface ontouch-sensitive display unit 1920, wherein the remote camerauser-interface comprises a shutter affordance; receive (e.g., with datareceiving unit 1936) data representing an image feed from a camera ofthe external device; and enable (e.g., with display enabling unit 1930)display of the image feed in the remote camera user-interface.Processing unit 1924 is further configured to: detect (e.g., with inputdetecting unit 1932) a gesture at a location corresponding to theshutter affordance; and in response to the detection of a gesture at alocation corresponding to the shutter affordance: transmit (e.g., withtransmitting unit 1938) an image capture request to the external device,the image capture request associated with an image capture time; and end(e.g., with display enabling unit 1930) the display of the image feedbefore the image capture time.

In some embodiments, ending the display of the image feed comprisesreplacing (e.g., with display enabling unit 1930) the display of theremote camera user-interface with a display of a screen selected fromthe group consisting of a home screen, a blank screen, and a watch face.

In some embodiments, ending the display of the image feed comprisesturning off (e.g., with display enabling unit 1930) touch-sensitivedisplay unit 1920.

In some embodiments, electronic device 1900 further comprises arotatable input mechanism unit 1922. Processing unit is furtherconfigured to: detect (e.g., with input detecting unit 1932) movement ofrotatable input mechanism unit 1922; and in response to the detection ofmovement of rotatable input mechanism unit 1922: resize (e.g., withdisplay enabling unit 1930) the display of the image feed in the remotecamera user-interface.

In some embodiments, processing unit 1926 is further configured to: inresponse to the detection of movement of rotatable input mechanism unit1922: transmit (e.g., with transmitting unit 1938) a zoom settingselection to the external device.

In some embodiments, processing unit 1926 is further configured to: inresponse to the detection of a gesture at a location corresponding tothe shutter affordance: transmit (e.g., with transmitting unit 1938) thezoom setting selection with the image capture request.

In some embodiments, processing unit 1926 is further configured to: inresponse to the detection of movement of rotatable input mechanism unit1922: transmit (e.g., with transmitting unit 1938) a focus settingselection to the external device.

In some embodiments, the remote camera user-interface comprises a toggleaffordance, and processing unit 1926 is further configured to: detect(e.g., with input detecting unit 1932) a gesture at a locationcorresponding to the toggle affordance; and in response to the detectionof a gesture at a location corresponding to the toggle affordance:change (with action changing unit 1940) an action associated withdetecting movement of rotatable input mechanism unit 1922, wherein theaction comprises one of resizing (e.g., with display enabling unit 1930)the display of the image feed in the remote camera user-interface andtransmitting (e.g., with transmitting unit 1938) a focus settingselection to the external device.

In some embodiments, processing unit 1926 is further configured to:detect (e.g., with input detecting unit 1932) a gesture at a locationcorresponding to the display of the image feed; and in response to thedetection of a gesture at a location corresponding to the display of theimage feed: transmit (e.g., with transmitting unit 1938) a focus settingselection to the external device.

In some embodiments, the remote camera user-interface comprises a flashaffordance, and processing unit 1926 is further configured to: detect(e.g., with input detecting unit 1932) a gesture at a locationcorresponding to the flash affordance; and in response to the detectionof a gesture at a location corresponding to the flash affordance:transmit (e.g., with transmitting unit 1938) a camera flash selection tothe external device, wherein the camera flash selection comprises anauto/on/off setting of a camera flash of the external device.

In some embodiments, the remote camera user-interface comprises a timeraffordance, and processing unit 1926 is further configured to: detect(e.g., with input detecting unit 1932) a gesture at a locationcorresponding to the timer affordance; and in response to the detectionof a gesture at a location corresponding to the timer affordance and tothe detection of a gesture at a location corresponding to the shutteraffordance: delay transmission (e.g., with transmitting unit 1938) ofthe image capture request.

In some embodiments, delaying transmission of the image capture requestcomprises delaying the transmission by one selected from a two-seconddelay and a ten-second delay.

In some embodiments, the remote camera user-interface comprises a timeraffordance, and processing unit 1926 is further configured to: detect(e.g., with input detecting unit 1932) a gesture at a locationcorresponding to the timer affordance; and in response to the detectionof a gesture at a location corresponding to the timer affordance and tothe detection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 1938) a requestedimage capture time with the image capture request, wherein the requestedimage capture time accounts for a timer setting associated with thetimer affordance.

In some embodiments, the timer setting is one selected from a two-secondtimer setting and a ten-second timer setting.

In some embodiments, processing unit 1926 is further configured to: inresponse to the detection of a gesture at a location corresponding tothe shutter affordance, enable (e.g., with display enabling unit 1930)display of a count-down to the image capture time.

In some embodiments, processing unit 1926 is further configured to: inaccordance with a determination that electronic device 1900 is notwirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance, enable (e.g., with display enabling unit 1930) display of anotification that the external device is not available for remote cameracontrol.

In some embodiments, processing unit 1926 is further configured to:further in accordance with a determination that electronic device 1900is not wirelessly connected to the external device and in response tothe detection of a gesture at a location corresponding to the cameraaffordance: enable (e.g., with display enabling unit 1930) display of animage preview affordance; and detect (e.g., with input detecting unit1932) a gesture at a location corresponding to the image previewaffordance. Processing unit 1926 is further configured to: in responseto the detection of a gesture at a location corresponding to the imagepreview affordance: enable (e.g., with display enabling unit 1930)display of one or more images of a photo album stored on electronicdevice 1900.

In some embodiments, the remote camera user-interface comprises an imagepreview affordance, and processing unit 1926 is further configured to:detect (e.g., with input detecting unit 1932) a gesture at a locationcorresponding to the image preview affordance; and in response to thedetection of a gesture at a location corresponding to the image previewaffordance: enable (e.g., with display enabling unit 1930) display ofone or more images of a photo album of the external device.

In some embodiments, the image preview affordance comprises a thumbnailof an image of the photo album of the external device.

In some embodiments, the image capture request comprises a requestedimage capture time.

In some embodiments, ending the display of the image feed occurs priorto transmitting the image capture request to the external device.

In some embodiments, detecting a gesture at a location corresponding tothe camera affordance comprises detecting a contact on the cameraaffordance and detecting liftoff of the contact.

The operations described above with reference to FIG. 15 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.19. For example, displaying operation 1502, contact detecting operation1504, and determining operation 1506 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 20 shows an exemplaryfunctional block diagram of an electronic device 2000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2000 are configured to perform the techniques described above.The functional blocks of the device 2000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 20 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 20, an electronic device 2000 includes atouch-sensitive display unit 2020 configured to display a graphic userinterface, a rotatable mechanism unit 2022, and a processing unit 2026coupled to touch-sensitive display unit 2020 and rotatable mechanismunit 2022. In some embodiments, processing unit 2026 includes a displayenabling unit 2030, an input detecting unit 2032, a wireless connectiondetermining unit 2034, and a data receiving unit 2036. Optionally,processing unit 2026 also includes a transmitting unit 2038 and anaction changing unit 2040.

Processing unit 2026 is configured to: enable (e.g., with displayenabling unit 2030) display of a camera affordance on touch-sensitivedisplay unit 2020; detect (e.g., with input detecting unit 2032) agesture at a location corresponding to the camera affordance; determine(e.g., with wireless connection determining unit 2034) whetherelectronic device 2000 is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat electronic device 2000 is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: enable (e.g., with displayenabling unit 2030) display of a remote camera user-interface ontouch-sensitive display unit 2020; receive (e.g., with data receivingunit 2036) data representing an image feed from a camera of the externaldevice; and enable (e.g., with display enabling unit 2030) display ofthe image feed in the remote camera user-interface. Processing unit 2026is further configured to: detect (e.g., with input detecting unit 2032)movement of rotatable input mechanism unit 2022; and in response to thedetection of movement of rotatable input mechanism unit 2022: resize(e.g., with display enabling unit 2030) a display of the image feed inthe remote camera user-interface.

In some embodiments, processing unit 2026 is further configured to: inresponse to the detection of movement of rotatable input mechanism unit2022: transmit (e.g., with transmitting unit 2038) a zoom settingselection to the external device.

In some embodiments, the remote camera user-interface comprises ashutter affordance, and processing unit 2026 is further configured to:detect (e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 2038) an imagecapture request to the external device; and transmit (e.g., withtransmitting unit 2038) the zoom setting selection with the imagecapture request.

In some embodiments, the remote camera user-interface comprises a toggleaffordance, and processing unit 2026 is further configured to: detect(e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the toggle affordance; and in response to the detectionof a gesture at a location corresponding to the toggle affordance:change (e.g., with action changing unit 2040) an action associated withdetecting movement of rotatable input mechanism unit 2022, wherein theaction comprises one of resizing (e.g., with display enabling unit 2030)the display of the image feed in the remote camera user-interface andtransmitting (e.g., with transmitting unit 2038) a focus settingselection to the external device.

In some embodiments, processing unit 2026 is further configured to:detect (e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the display of the image feed; and in response to thedetection of a gesture at a location corresponding to the display of theimage feed: transmit (e.g., with transmitting unit 2038) a focus settingselection to the external device.

In some embodiments, the remote camera user-interface comprises ashutter affordance, and processing unit 2026 is further configured to:detect (e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 2038) an imagecapture request to the external device.

In some embodiments, the remote camera user-interface comprises ashutter affordance, and processing unit 2026 is further configured to:detect (e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 2038) an imagecapture request to the external device, the image capture requestassociated with an image capture time; and end (e.g., with displayenabling unit 2030) the display of the image feed before the imagecapture time.

In some embodiments, the image capture request comprises a requestedimage capture time.

In some embodiments, ending the display of the image feed occurs priorto transmitting the image capture request to the external device.

In some embodiments, the remote camera user-interface comprises a flashaffordance, and processing unit 2026 is further configured to: detect(e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the flash affordance; and in response to the detectionof a gesture at a location corresponding to the flash affordance:transmit (e.g., with transmitting unit 2038) a camera flash selection tothe external device, wherein the camera flash selection comprises anauto/on/off setting of a camera flash of the external device.

In some embodiments, the remote camera user-interface comprises a timeraffordance and a shutter affordance, and processing unit 2026 is furtherconfigured to: detect (e.g., with input detecting unit 2032) a gestureat a location corresponding to the timer affordance; detect (e.g., withinput detecting unit 2032) a gesture at a location corresponding to theshutter affordance; and in response to the detection of a gesture at alocation corresponding to the timer affordance and to the detection of agesture at a location corresponding to the shutter affordance: delay(e.g., with transmitting unit 2038) transmission of the image capturerequest.

In some embodiments, delaying transmission of the image capture requestcomprises delaying the transmission by one selected from a two-seconddelay and a ten-second delay.

In some embodiments, the remote camera user-interface comprises a timeraffordance and a shutter affordance, and processing unit 2026 is furtherconfigured to: detect (e.g., with input detecting unit 2032) a gestureat a location corresponding to the timer affordance; detect (e.g., withinput detecting unit 2032) a gesture at a location corresponding to theshutter affordance; and in response to the detection of a gesture at alocation corresponding to the timer affordance and to the detection of agesture at a location corresponding to the shutter affordance: transmit(e.g., with transmitting unit 2038) a requested image capture time withan image capture request, wherein the requested image capture timeaccounts for a timer setting associated with the timer affordance.

In some embodiments, the timer setting is one selected from a two-secondtimer setting and a ten-second timer setting.

In some embodiments, processing unit 2026 is further configured to: inresponse to the detection of a gesture at a location corresponding tothe shutter affordance: enable (e.g., with display enabling unit 2030)display of a count-down to the image capture time.

In some embodiments, the remote camera user-interface comprises an imagepreview affordance, and processing unit 2026 is further configured to:detect (e.g., with input detecting unit 2032) a gesture at a locationcorresponding to the image preview affordance; and in response to thedetection of a gesture at a location corresponding to the image previewaffordance: enable (e.g., with display enabling unit 2030) display ofone or more images of a photo album of the external device.

In some embodiments, the image preview affordance comprises a thumbnailof an image of the photo album of the external device.

In some embodiments, processing unit 2026 is further configured to: inaccordance with a determination that electronic device 2000 is notwirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: enable (e.g., with display enabling unit 2030) display of anotification that the external device is not responsive to remote cameracontrol.

In some embodiments, processing unit 2026 is further configured to:further in accordance with a determination that electronic device 2000is not wirelessly connected to the external device and in response tothe detection of a gesture at a location corresponding to the cameraaffordance: enable (e.g., with display enabling unit 2030) display of animage preview affordance; and detect (e.g., with input detecting unit2032) a gesture at a location corresponding to the image previewaffordance. Processing unit 2026 is further configured to: in responseto the detection of a gesture at a location corresponding to the imagepreview affordance: enable (e.g., with display enabling unit 2030)display of one or more images of a photo album stored on electronicdevice 2000.

In some embodiments, detecting a gesture at a location corresponding tothe camera affordance comprises detecting (e.g., with input detectingunit 2032) a contact on the camera affordance and detecting (e.g., withinput detecting unit 2032) liftoff of the contact.

The operations described above with reference to FIG. 16 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.20. For example, displaying operation 1602, contact detecting operation1604, and determining operation 1606 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 21 shows an exemplaryfunctional block diagram of an electronic device 2100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2100 are configured to perform the techniques described above.The functional blocks of the device 2100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 21 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 21, an electronic device 2100 includes atouch-sensitive display unit 2120 configured to display a graphic userinterface, a rotatable mechanism unit 2122, and a processing unit 2126coupled to touch-sensitive display unit 2120 and rotatable mechanismunit 2122. In some embodiments, processing unit 2126 includes a displayenabling unit 2130, an input detecting unit 2132, a wireless connectiondetermining unit 2134, a data receiving unit 2136 and a transmittingunit 2138. Optionally, processing unit 2126 also includes an actionchanging unit 2140.

Processing unit 2126 is configured to: enable (e.g., with displayenabling unit 2130) display of a camera affordance on touch-sensitivedisplay unit 2120; detect (e.g., with input detecting unit 2132) agesture at a location corresponding to the camera affordance; determine(e.g., with wireless connection determining unit 2134) whetherelectronic device 2100 is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat electronic device 2100 is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: enable (e.g., with displayenabling unit 2130) display of a remote camera user-interface ontouch-sensitive display unit 2120; receive (e.g., with data receivingunit 2136) data representing an image feed from a camera of the externaldevice; and enable (e.g., with display enabling unit 2130) display ofthe image feed in the remote camera user-interface. Processing unit 2126is further configured to: detect movement of rotatable input mechanismunit 2122; and in response to the detection of movement of rotatableinput mechanism unit 2122: transmit (e.g., with transmitting unit 2138)a focus setting selection to the external device.

In some embodiments, the remote camera user-interface comprises ashutter affordance, and processing unit 2126 is further configured to:detect (e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 2138) an imagecapture request to the external device, the image capture requestassociated with an image capture time; and transmit (e.g., withtransmitting unit 2138) the focus setting selection with the imagecapture request.

In some embodiments, the remote camera user-interface comprises a toggleaffordance, and processing unit 2126 is further configured to: detect(e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the toggle affordance; and in response to the detectionof a gesture at a location corresponding to the toggle affordance:change (e.g., with action changing unit 2140) an action associated withdetecting movement of rotatable input mechanism unit 2122, wherein theaction comprises one of resizing the display of the image feed in theremote camera user-interface and transmitting a focus setting selectionto the external device.

In some embodiments, processing unit 2126 is further configured to:detect (e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the display of the image feed; and in response to thedetection of a gesture at a location corresponding to the display of theimage feed: transmit (e.g., with transmitting unit 2138) a focus settingselection to the external device.

In some embodiments, the remote camera user-interface comprises ashutter affordance, and processing unit 2126 is further configured to:detect (e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 2138) an imagecapture request to the external device.

In some embodiments, the remote camera user-interface comprises ashutter affordance, and processing unit 2126 is further configured to:detect (e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit (e.g., with transmitting unit 2138) an imagecapture request to the external device, the image capture requestassociated with an image capture time; and end (e.g., with displayenabling unit 2130) the display of the image feed before the imagecapture time.

In some embodiments, the image capture request comprises a requestedimage capture time.

In some embodiments, ending the display of the image feed occurs priorto transmitting the image capture request to the external device.

In some embodiments, the remote camera user-interface comprises a flashaffordance, and processing unit 2126 is further configured to: detect(e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the flash affordance; and in response to the detectionof a gesture at a location corresponding to the flash affordance:transmit (e.g., with transmitting unit 2138) a camera flash selection tothe external device, wherein the camera flash selection comprises anauto/on/off setting of a camera flash of the external device.

In some embodiments, the remote camera user-interface comprises a timeraffordance and a shutter affordance, and processing unit 2126 is furtherconfigured to: detect (e.g., with input detecting unit 2132) a gestureat a location corresponding to the timer affordance; detect (e.g., withinput detecting unit 2132) a gesture at a location corresponding to theshutter affordance; and in response to the detection of a gesture at alocation corresponding to the timer affordance and to the detection of agesture at a location corresponding to the shutter affordance: delay(e.g., with transmitting unit 2138) transmission of the image capturerequest.

In some embodiments, delaying transmission of the image capture requestcomprises delaying the transmission by one selected from a two-seconddelay and a ten-second delay.

In some embodiments, the remote camera user-interface comprises a timeraffordance and a shutter affordance, and processing unit 2126 is furtherconfigured to: detect (e.g., with input detecting unit 2132) a gestureat a location corresponding to the timer affordance; detect (e.g., withinput detecting unit 2132) a gesture at a location corresponding to theshutter affordance; and in response to the detection of a gesture at alocation corresponding to the timer affordance and to the detection of agesture at a location corresponding to the shutter affordance: transmit(e.g., with transmitting unit 2138) a requested image capture time withan image capture request, wherein the requested image capture timeaccounts for a timer setting associated with the timer affordance.

In some embodiments, the timer setting is one selected from a two-secondtimer setting and a ten-second timer setting.

In some embodiments, processing unit 2126 is further configured to: inresponse to the detection of a gesture at a location corresponding tothe shutter affordance: enable (e.g., with display enabling unit 2130)display of a count-down to the image capture time.

In some embodiments, the remote camera user-interface comprises an imagepreview affordance, and processing unit 2126 is further configured to:detect (e.g., with input detecting unit 2132) a gesture at a locationcorresponding to the image preview affordance; and in response to thedetection of a gesture at a location corresponding to the image previewaffordance: enable (e.g., with display enabling unit 2130) display ofone or more images of a photo album of the external device.

In some embodiments, the image preview affordance comprises a thumbnailof an image of the photo album of the external device.

In some embodiments, processing unit 2126 is further configured to: inaccordance with a determination that electronic device 2100 is notwirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: enable (e.g., with display enabling unit 2130) display of anotification that the external device is not responsive to remote cameracontrol.

In some embodiments, processing unit 2126 is further configured to:further in accordance with a determination that electronic device 2100is not wirelessly connected to the external device and in response tothe detection of a gesture at a location corresponding to the cameraaffordance: enable (e.g., with display enabling unit 2130) display of animage preview affordance; and detect (e.g., with input detecting unit2132) a gesture at a location corresponding to the image previewaffordance. Processing unit 2126 is further configured to: in responseto the detection of a gesture at a location corresponding to the imagepreview affordance: enable (e.g., with display enabling unit 2130)display of one or more images of a photo album stored on electronicdevice 2100.

In some embodiments, detecting a gesture at a location corresponding tothe camera affordance comprises detecting (e.g., with input detectingunit 2132) a contact on the camera affordance and detecting (e.g., withinput detecting unit 2132) liftoff of the contact.

The operations described above with reference to FIG. 17 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.21. For example, displaying operation 1702, detecting operation 1704,and determining operation 1706 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a touch-sensitive display, cause the device to:display a camera affordance on the touch-sensitive display; detect agesture at a location corresponding to the camera affordance; determinewhether the electronic device is wirelessly connected to an externaldevice responsive to remote camera control; in accordance with adetermination that the electronic device is wirelessly connected to theexternal device and in response to the detection of a gesture at alocation corresponding to the camera affordance: display a remote camerauser-interface on the touch-sensitive display, wherein the remote camerauser-interface comprises a shutter affordance; receive data representingan image feed from a camera of the external device; and display theimage feed in the remote camera user-interface; detect a gesture at alocation corresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit an image capture request to the external device,the image capture request associated with an image capture time; and endthe display of the image feed before the image capture time.
 2. Thenon-transitory computer readable storage medium of claim 1, whereinending the display of the image feed comprises replacing the display ofthe remote camera user-interface with a display of a screen selectedfrom the group consisting of a home screen, a blank screen, and a watchface.
 3. The non-transitory computer readable storage medium of claim 1,wherein ending the display of the image feed comprises turning off thedisplay.
 4. The non-transitory computer readable storage medium of claim1, wherein the electronic device further comprises a rotatable inputmechanism, and wherein the one or more programs comprise instructionsthat cause the device to: detect movement of the rotatable inputmechanism; and in response to the detection of movement of the rotatableinput mechanism: resize the display of the image feed in the remotecamera user-interface.
 5. The non-transitory computer readable storagemedium of claim 4, wherein the one or more programs compriseinstructions that cause the device to: in response to the detection ofmovement of the rotatable input mechanism: transmit a zoom settingselection to the external device.
 6. The non-transitory computerreadable storage medium of claim 5, wherein the one or more programscomprise instructions that cause the device to: in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmit the zoom setting selection with the image capturerequest.
 7. The non-transitory computer readable storage medium of claim4, wherein the one or more programs comprise instructions that cause thedevice to: in response to the detection of movement of the rotatableinput mechanism: transmit a focus setting selection to the externaldevice.
 8. The non-transitory computer readable storage medium of claim7, wherein the remote camera user-interface comprises a toggleaffordance, and wherein the one or more programs comprise instructionsthat cause the device to: detect a gesture at a location correspondingto the toggle affordance; and in response to the detection of a gestureat a location corresponding to the toggle affordance: change an actionassociated with detecting movement of the rotatable input mechanism,wherein the action comprises one of resizing the display of the imagefeed in the remote camera user-interface and transmitting a focussetting selection to the external device.
 9. The non-transitory computerreadable storage medium of claim 1, wherein the one or more programscomprise instructions that cause the device to: detect a gesture at alocation corresponding to the display of the image feed; and in responseto the detection of a gesture at a location corresponding to the displayof the image feed: transmit a focus setting selection to the externaldevice.
 10. The non-transitory computer readable storage medium of claim1, wherein the remote camera user-interface comprises a flashaffordance, and wherein the one or more programs comprise instructionsthat cause the device to: detect a gesture at a location correspondingto the flash affordance; and in response to the detection of a gestureat a location corresponding to the flash affordance: transmit a cameraflash selection to the external device, wherein the camera flashselection comprises an auto/on/off setting of a camera flash of theexternal device.
 11. The non-transitory computer readable storage mediumof claim 1, wherein the remote camera user-interface comprises a timeraffordance, and wherein the one or more programs comprise instructionsthat cause the device to: detect a gesture at a location correspondingto the timer affordance; and in response to the detection of a gestureat a location corresponding to the timer affordance and to the detectionof a gesture at a location corresponding to the shutter affordance:delay transmission of the image capture request.
 12. The non-transitorycomputer readable storage medium of claim 11, wherein delayingtransmission of the image capture request comprises delaying thetransmission by one selected from a two-second delay and a ten-seconddelay.
 13. The non-transitory computer readable storage medium of claim1, wherein the remote camera user-interface comprises a timeraffordance, and wherein the one or more programs comprise instructionsthat cause the device to: detect a gesture at a location correspondingto the timer affordance; and in response to the detection of a gestureat a location corresponding to the timer affordance and to the detectionof a gesture at a location corresponding to the shutter affordance:transmit a requested image capture time with the image capture request,wherein the requested image capture time accounts for a timer settingassociated with the timer affordance.
 14. The non-transitory computerreadable storage medium of claim 13, wherein the timer setting is oneselected from a two-second timer setting and a ten-second timer setting.15. The non-transitory computer readable storage medium of claim 11,wherein the one or more programs comprise instructions that cause thedevice to: in response to the detection of a gesture at a locationcorresponding to the shutter affordance: display a count-down to theimage capture time.
 16. The non-transitory computer readable storagemedium of claim 1, wherein the one or more programs compriseinstructions that cause the device to: in accordance with adetermination that the electronic device is not wirelessly connected tothe external device and in response to the detection of a gesture at alocation corresponding to the camera affordance: display a notificationthat the external device is not available for remote camera control. 17.The non-transitory computer readable storage medium of claim 16, whereinthe one or more programs comprise instructions that cause the device to:further in accordance with a determination that the electronic device isnot wirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: display an image preview affordance; and detect a gesture ata location corresponding to the image preview affordance; and inresponse to the detection of a gesture at a location corresponding tothe image preview affordance: display one or more images of a photoalbum stored on the electronic device.
 18. The non-transitory computerreadable storage medium of claim 1, wherein the remote camerauser-interface comprises an image preview affordance, and wherein theone or more programs comprise instructions that cause the device to:detect a gesture at a location corresponding to the image previewaffordance; and in response to the detection of a gesture at a locationcorresponding to the image preview affordance: display one or moreimages of a photo album of the external device.
 19. The non-transitorycomputer readable storage medium of claim 18, wherein the image previewaffordance comprises a thumbnail of an image of the photo album of theexternal device.
 20. The non-transitory computer readable storage mediumof claim 1, wherein the image capture request comprises a requestedimage capture time.
 21. The non-transitory computer readable storagemedium of claim 1, wherein ending the display of the image feed occursprior to transmitting the image capture request to the external device.22. The non-transitory computer readable storage medium of claim 1,wherein detecting a gesture at a location corresponding to the cameraaffordance comprises detecting a contact on the camera affordance anddetecting liftoff of the contact.
 23. A method, comprising: at anelectronic device with a touch-sensitive display: displaying a cameraaffordance on the touch-sensitive display; detecting a gesture at alocation corresponding to the camera affordance; determining whether theelectronic device is wirelessly connected to an external deviceresponsive to remote camera control; in accordance with a determinationthat the electronic device is wirelessly connected to the externaldevice and in response to the detection of a gesture at a locationcorresponding to the camera affordance: displaying a remote camerauser-interface on the touch-sensitive display, wherein the remote camerauser-interface comprises a shutter affordance; receiving datarepresenting an image feed from a camera of the external device; anddisplaying the image feed in the remote camera user-interface; detectinga gesture at a location corresponding to the shutter affordance; and inresponse to the detection of a gesture at a location corresponding tothe shutter affordance: transmitting an image capture request to theexternal device, the image capture request associated with an imagecapture time; and ending the display of the image feed before the imagecapture time.
 24. An electronic device, comprising: a touch-sensitivedisplay; one or more processors; a memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions for: displaying a camera affordance on thetouch-sensitive display; detecting a gesture at a location correspondingto the camera affordance; determining whether the electronic device iswirelessly connected to an external device responsive to remote cameracontrol; in accordance with a determination that the electronic deviceis wirelessly connected to the external device and in response to thedetection of a gesture at a location corresponding to the cameraaffordance: displaying a remote camera user-interface on thetouch-sensitive display, wherein the remote camera user-interfacecomprises a shutter affordance; receiving data representing an imagefeed from a camera of the external device; and displaying the image feedin the remote camera user-interface; detecting a gesture at a locationcorresponding to the shutter affordance; and in response to thedetection of a gesture at a location corresponding to the shutteraffordance: transmitting an image capture request to the externaldevice, the image capture request associated with an image capture time;and ending the display of the image feed before the image capture time.